Release notes
You can download a PDF version of the release notes here.
TIP: Looking for release notes for all Axiom products, including current previous versions? Click here.
About the release notes
Syntellis is pleased to announce the 2022.1 release of Axiom Rolling Forecasting. Each product release provides new features, enhancements, and configuration options to meet your needs. Many of these features and enhancements are a direct result of your feedback and suggestions.
The purpose of these release notes is to provide you with the following:
- High-level descriptions of new features
- Information to know before upgrading
- Steps for preparing for and scheduling your upgrade
- List of fixed issues
TIP: Periodically, the release notes are updated when new information is available, including patch release fixes. To view the latest release notes, we encourage you to view them in the Axiom Rolling Forecasting online help. On the help home page, click the Release Notes link at the top of the page.
New features in Axiom Rolling Forecasting
See What’s New.
What to know before upgrading
IMPORTANT: You must apply the Axiom 2022.1 upgrade before applying any 2022.1 Axiom product upgrades. Axiom upgrades are backward compatible so you can upgrade different products at different times, but you must upgrade to Axiom 2022.1 before the first product upgrade. Refer to the Axiom 2022.1 Release Notes and Axiom Healthcare Suite 2022.1 Release Notes for consideration before upgrading.
When upgrading to the 2022.1 version of Axiom Rolling Forecasting, note the following:
- You can replace Syntellis reports. Any report that you created or saved under a different name remains unchanged. Revised reports are available in Document History.
- Any Syntellis report that was moved to a new location is automatically moved back to its original location.
- Syntellis product templates and calculation method libraries are replaced.
- Product task panes are replaced.
- Process definitions are not replaced.
- Driver files are replaced.
- Security roles and subsystems are reset to their configured settings. Your user security exceptions remain intact.
- Specific items that are configured as part of your company or organization’s implementation such as imports, exports, driver files, and process management files, remain unchanged. Any required modifications to these areas are covered in the release notes.
Preparing and scheduling upgrades
Summary of the upgrade process:
- Review product release notes – Review this document to become familiar with the new features and functionality.
- Schedule an installation date – Submit a request to your organization’s Axiom System Administrator to contact Support by creating a support ticket to schedule an installation date and time with at least three days of advance notice. The request should include the following information:
- Axiom platform version.
- Axiom for Healthcare product and version.
- Whether to first refresh and apply updates to the Axiom test sandbox with a copy of the production instance of Axiom. If so, provide the earliest date that Syntellis can do this.
- Propose an approximate two-hour downtime window when Syntellis can apply updates to the production instance of Axiom during regular business hours, Monday through Friday 7 AM to 7 PM Central (except holidays recognized by Syntellis).
- Complete manual configuration updates – After installing the upgrade, review any manual setup steps to enable features for this version.
Getting help and training
Syntellis provides world-class resources directly within the Axiom system. Axiom Help provides topics, knowledge base articles, documents, webinar/training announcements, and videos to guide you through managing your system. To access these resources, do any of the following:
-
Windows and Excel Clients – From the Main or Admin ribbon tab, click Online Help, and then select the product. Axiom Help opens in a new browser window.
NOTE: The online help opens only for products you are licensed to use.
-
Contextual help – Form/web-enabled features and products include contextual help directly within the user interface. This information provides a quick summary and instructions specifically related to the page you are using. You can access this information by clicking the question mark in the upper right corner of the page. To access the full Axiom Help system, click Open Help at the top of the contextual help dialog.
Syntellis Central
Syntellis Central provides centralized self-service content and resources for the Axiom Rolling Forecasting platform and suite of products. Using Syntellis Central, you can:
-
Search help across all Axiom products.
-
Access tips, tricks, and best practices in our knowledge base.
-
Find training and certification content including on-demand, video, webinars, labs, and instructor-led courses.
-
Submit a Support issue, find suggested content, and manage any outstanding issues directly with Support.
-
Review open Software Service project status and details.
Issues fixed in 2022.1
The following table lists the resolutions for issues addressed in 2022.1, released May 23, 2022:
Calculators
| Issue | Description |
|---|---|
| Remove BSCF from 2022.1 due to newly found issues [128331] |
Summary: The Balance Sheet and Cash Flow calculator has been disabled for this release so that we can prepare for an improved version of the calculator in an upcoming release. Resolution: Removed the Balance Sheet and Cash Flow calculator from the product. |
| Add helpful 000 indicator label to prevent confusion in RF Deductions Calculator [115363] |
Summary: In the Deductions sheet of the Deductions Model calculator, when a user enters a natural number (scale = 1) instead of a scaled value, unexpected data results. Resolution: For the rows that need it, added a number scale indicator ($000s) in the row headings so the user has a visual cue of the format to use. |
| [T3] Case Number 00453245 - PFB: RF Deduction Model IP Medicare CMI historical values change to 1.0000 when modified to Last Saved [125104] |
Summary: In the Deductions sheet of the Deductions Model calculator, in the IP Medicare section on the CMI Index row (DRG), when a user changes the Data Selection/Forecast Method from Default to Last Save, the historical CMI values no longer tie to the actuals; instead, they are changed to 1. This is caused by missing business logic where the DRG CMI calculation differs from the CMI calculation for actual periods. Resolution: Corrected by updating the logic to reference the four cells above each actual period monthly cell. |
| (2022.1) [T3] Case Number 00461832 - PFB RF Deduction Model - Bad Debt and Charity [134770] |
Summary: In the Deductions sheet of the Deductions Model calculator, in the variable actual/forecast columns, Charity and Bad Debt are not calculating correctly because they are referencing the wrong cells. Resolution: Corrected by updating the formulas to reference the right cells. |
| [T3] Case Number 00462576 - RF Defect: Admin Adj in Ded utility not functioning as expected [134985] |
Summary: In the Administrative Adjustments section of the RF Deductions Setup utility, when a user has selected Total in the drop-down, the Deductions Model calculator only calculates against the IP Gross Charges. The calculation in the calculator is only dividing by IP revenue regardless of what is selected in the setup utility. Resolution: Corrected by modifying the formula to calculate correctly when Total is selected. Updated for all historical and actual columns, both months and quarters, and the quarterly forecast columns. |
Drivers
| Issue | Description |
|---|---|
| RF2.0 Benefits Calc Methods, Pct of Salaries and Rate per FTE, should exclude Contractual Salaries and FTEs [120048] |
Summary: In the plan file Forecast worksheet, the Pct of Salaries calculation method and the Rate per FTE calculation method use the total Salary/FTE values to compute the benefits. Users want the option to exclude contractual labor from the total salaries calculation. Resolution: Corrected by updating the calculation methods so that the user does not need to select a benefits code when the selected Salary code is E_Salaries_Contract. |
| Global Data issues with Forecast tab not combining codes and duplicate issues in the Global Data driver [123134, 142380, 140732 (2021.3)] |
Summary: When the global data calculation method is used in a plan file, the data coming from the driver is not KHABgtCode compliant. Resolution: Corrected by updating the Global Data calculation method to be RFCode.KHABgtCode compliant. It now only allows insertion of RFCodes where ForecastStdLine = Global Data and RFCodes that exist in KHABgtCode column. If data in the Global Data driver was stored at the RFCode level, the plan file was updated to bring consolidated results from the driver table at the KHABgtCode level. Subsequently, we updated the Update Global Data utility to consolidate records and save data at the RFCode.KHABgtCode level, and to delete orphaned records (where RFCode does not equal KHABgtCode). |
| RF Driver Codes tab in Code Mapping driver- Picklist allows selection of adjustment codes as Drivers for IP, OP and Other and showing up in plan files [134697] |
Summary: When users add a new driver forecast assumption in the Drivers tab of the Drivers setup utility, and then go to the Code Mapping tab to map the assumptions to driver codes, they are able to select adjustment codes from the Driver Codes menu. This should not be possible because it creates invalid drivers in the plan file. Resolution: Corrected by adding a data filter to the driver code menu code that excludes adjustments. |
Plan files – Forecast
| Issue | Description |
|---|---|
| (2022.1) RF 2.0 OTA in Salary Exp not flowing down to Benefits [118896] |
Summary: In the plan file Forecast worksheet, if a user adds a one-time adjustment in the Salary block, the value impact of that adjustment does not get picked up in the Benefits calculation methods Pct of Salaries and Rate per FTE. Resolution: Corrected by adjusting the applicable formulas so that the One Time Adjustment totals in the Salary blocks flow through to the Benefits sections and are included in the calculations. |
| [T3] Case Number 00449076 - PFB to be Submitted - RF Expense Calc Method - Adjustments [118918] |
Summary: In the plan file Forecast worksheet expense sections, when a user makes a one-time adjustment to an Actual period, the adjustment is being included in the total line, which saves to the Forecast Final RFDType, which is changing the actual values. One-time adjustments should not affect the final total amount. Resolution: Corrected by updating the formulas so that the one-time adjustments are not included in the final total amount for Actual periods. |
| (2022.1) [T3] Case Number 00449082 - PFB to be Submitted - RF Expense Calc Method - Variable Rate [119273] |
Summary: In the plan file Forecast worksheet, when a user sets an expense to something other than 0% or 100% in the Fixed/Variable column, the variable rate calculates too low. When calculating the historical fixed and variable expense, it takes the fixed/variable ratio into account. Then the formula that calculates the variable rate multiplies the variable expense by the variable percentage again, which reduces the rate to half of what it should be. Resolution: Corrected by adjusting the calculation to remove the multiplication of the variable ratio. |
| [2022.1] RF 2.0 OTA in Stats not influencing Salary Expense [119961] |
Summary: In the plan file Forecast worksheet under Patient Days, the informational line “Impact of Volume OTA” for the Salary calculation method is supposed to display the effect of one-time adjustments (OTAs) in the Volume calculation method on the salary projections. However, the formula is missing the variable hours per unit factor so the amount displayed is not correct. Resolution: Corrected by updating the formula to include the variable hours per unit adjusted for productivity changes. |
| (2022.1) RF2.0 Rate per FTE Calc Method sums the monthly FTEs in the quarterly calculations. This is incorrect [120047] |
Summary: In the plan file Forecast worksheet, the Rate per FTE calculation method is summing the monthly FTEs in the quarterly columns. This is incorrect and is occurring in both actuals and forecast columns. Resolution: Corrected by updating the Rate per FTE calculation method to sum in the correct columns. |
| (2022.1) RF2.0 IP Census CM Quarterly Column Calculations incorrectly summing monthly results [120482] |
Summary: In the plan file Forecast worksheet, the calculation for the IP Census is incorrectly summing the quarterly columns. Resolution: Corrected by updating the formula so that the quarterly columns are calculated correctly. |
| RF Benefits CMs not including all the OTAs in the ForecastFinal RFDType Save [121463] |
Summary: The Benefits calculation methods Percent of Salaries and Rate per FTE are not saving the correct row to the RFDType “ForecastFinal” rows in the forecast tables. The values saving to this RFDType are incorrect, especially the FTE impact. The plan file Forecast and Summary sheets are displaying incorrect amounts as a result. Resolution: Corrected by moving the ForecastFinal save row to the correct final result row in the calculation methods. |
| [T3] Case Number 00450994 - PFB to be Submitted - RF Plan File Save Tags [121502] |
Summary: In the plan file Forecast worksheet, hours-related codes are not saving to the RFDType of ForecastFinal in the forecast tables. The hours rows in the plan file do not have an associated save tag. Resolution: Corrected by adding the needed save tags to the plan file template. |
| Patient Revenue CM double counts the inflation rate and adjustments in the average rate per unit calculation in the forecast periods of the current quarter [125048] |
Summary: In the plan file Forecast worksheet, in the forecasted columns of the current quarter, the Patient Revenue calculation method is double counting the inflation rate and the adjustments, causing the average rate per unit to be wrong. Resolution: Corrected by modifying the formulas in the Patient Revenue calculation method to remove double counting. |
| Forecast method labels for IP Census picklist selections in the Revenue CM blocks do not account for set up for discharges [127295] |
Summary: In the plan file Forecast worksheet, if a user has configured their RFCodes and related driver for IP Census to be Discharges when using the forecast method in the revenue block, the only option available is Admissions. However, the worksheet still pulls the correct data for discharges from the statistics section. The drop-down list in Patient Revenue should match what is in use. For example, if discharges are being used, then the label above should include Discharges. Resolution: Corrected by changing the CMI Inpatient Admissions label to CMI Inpatient Admits\Discharges and changing CMI Adjusted Admissions label to CMI Adjusted Admits\Discharges. |
| (2022.1) [T3] Case Number 00457931 - Forecast tab: RF 2.0 Benefits Quarterly values referencing a hardcoded 0 cell [130887] |
Summary: In the plan file Forecast worksheet, the quarterly % of Salaries do not display even when there are monthly dollars for Salary, Benefits, and monthly % of salary. Resolution: Corrected by updating the code so that the affected cells reference the correct rows and the zeros in the affected columns are not hard coded. |
| Forecast tab- Revenue Calc methods using CMI Inpatient Admits\Discharges forecast method results in circular reference [135236] |
Summary: In the Patient Revenue, Patient Revenue IP Census, and Patient Revenue Net Per Unit calc methods, a circular reference is being introduced when a user selects the CMI Adjusted Admits\Discharges or the CMI Inpatient Admits\Discharges to calculate the per unit ratio. Resolution: Corrected by removing the CMI Adjusted Admits\Discharges or the CMI Inpatient Admits\Discharges as options used to calculate the per unit ratio. |
| (2022.1 GA) [T3] Case Number 00466146 - On the Employee Benefit Rate per FTE line, the Actuals qtr columns sum the three months while the forecast quarter columns calculate the Rate per FTE [139973] |
Summary: In the plan file Forecast worksheet, on the Employee Benefit Rate per FTE line, the Actuals quarter columns are summing the three months, which is incorrect, while the forecast quarter columns are calculating the Rate per FTE for the quarter, which is correct. Resolution: Corrected by changing the quarterly results in forecast periods to reflect the total benefits for the quarter/FTEs for the quarter. Also changed the labels to reflect Benefits per FTE rather than Rate per FTE. |
Plan files – Initiatives
| Issue | Description |
|---|---|
| (2022.1) [T3] Case Number 00448088 - PFB To Be Submitted - RF Initiatives w/ Rolling Forward [117848] |
Summary: In the plan file Initiatives worksheet, when a forecast rolls to a new period, any periods that were forecasts but are now actuals should have their adjustments zeroed out and reset. Instead, the previous amounts are appearing in the Actuals columns and saving back to the database, causing errors. Resolution: Corrected by incorporating the same roll logic as is used in the Forecast worksheet. Any adjustment from a period that was a forecast in the prior run and is now an actual is zeroed out. |
| [T3] Case Number 00449062 - PFB to be Submitted - RF: RFCode Table, Delivered Assets [118920] |
Summary: In the RFCODE Dimension table, standard RFCodes that have the calculation type “Deduction” or “Other Deduction” in the RFType column are being delivered with the wrong calculation type in the corresponding InitStdLine column. The delivered calculation type is “Revenue” or “Line Item,” but it should be “Deduction.” This is causing issues in the plan file Initiatives worksheet. Resolution: Corrected by updating the calculation method to “Deduction” in the InitStdLine column for the affected RFCODEs. |
| (2022.1) RF Initiatives - SupportingData!AQ2 requires Refresh After Save=On to assist with default CalcMethodForRebuild compared to InitStdLine [121558] |
Summary: In the plan file Initiatives worksheet, when a user adds an initiative block (RF Group or RF Project), and then adds an RFCode that uses the Line Item calculation method such as Non-operating Revenue, and then saves, the plan file rebuilds with the last saved calculation method or CalcMethodforRebuild. This requires associated Axiom queries to refresh the sheet data. Resolution: Corrected by adjusting the related Axiom Query on SupportingData tab (AQ2) to refresh the sheet after the user saves the new initiatives block. |
|
Initiatives tab rebuild issues - disable calc method for rebuild logic and depend on associated dimension stdline [123478] |
Summary: After a rollforward period is finalized, in the plan file, suppose a user needs to change the RFCode calculation method for a given RFGroup. In the RFCODE table, the user changes the calculation method listed in the RFCode.ForecastStdLine or RFCode.InitStdLine column for the RFGroup. The user saves the table, opens the plan file Initiatives tab, saves the plan file, and then rebuilds the plan file. When the user opens the rebuilt plan file, they see that the RFGroup is still using the previous calculation method, not the new one. Resolution: Corrected by updating the code in the Axiom Query to allow for the calculation method set in the RFCode.ForecastStdLine or RFCode.InitStdLine column to determine the calculation method for the rebuild instead of the last saved calculation method. |
| (2022.1) RF Initiatives - Adjust logic for add new RF Group to prevent RFID save error - keys must be unique [125129] |
Summary: In the plan file Initiatives worksheet, a user adds two RFGroup initiative blocks, the second of which requires details or data to interface. The user then adds a supplemental calculation method within the second initiative block, saves and then views the blocks after rebuilding the plan files. The first initiative block does not interface with the data but the second block does. In the RFID dimension table, there are two records in sequential order, as expected. When the user adds a new RFGroup initiative block and saves, an error occurs because adding the third initiative results in a duplicate RFID entry. Resolution: Corrected by adding to the SupportingData tab (AQ8) an Axiom Query that identifies the existing RFIDs for the RFGroup and then refreshes after saving. Updated the calculation method row formula to detect the record ID for each RFID table entry and then start with the next ID that follows the last one when a new initiative block is added. |
Plan files – Plan
| Issue | Description |
|---|---|
| [T3] Case Number 00441958 - RF_Plan Tab Responses not saving to retrieving data when fiscal year is changed [112149] |
Summary: In the plan file Plan worksheet, a user creates and saves responses and then closes the plan file. If the user changes the fiscal period and then reopens the plan file, the comments on the Plan worksheet display as expected. However, if the user changes the fiscal year and then opens the plan file, the comments on the Plan worksheet are missing. Resolution: Corrected by removing the reference to the Year field in Axiom Query 2 of the calculation method sheet on the Plan tab of the plan file template. Also updated various other worksheets that were referencing incorrect cells or fields. |
|
RF Plan tab: Clear out responses from unused questions if they were previously used [122121] |
Summary: In the plan file Plan worksheet, when a user clears a planning question exception and then enters a new one, the cleared responses return because the cleared responses are not being removed from the underlying data tables. Resolution: Corrected by updating the code to save a blank response if a question is cleared by the user. |
Reporting
| Issue | Description |
|---|---|
| (2022.1) RF Manager Dashboard | Executive Overview - Dynamically disable Historical Analysis option to prevent users from encountering errors [119014] |
Summary: In the Manager Dashboard, a number of issues are causing problems with the display of historical performance analysis data in some of the Executive Overview tab’s KPI cards. This occurs:
Resolution: Corrected by disabling the display of historical analysis data in the affected KPI cards. The Historical Performance Analysis table will not display for these cards, nor will the related icon ( |
| RF Dashboard: Historical Analysis on Summary tab | Net Income Over Expenses with Total setting fails "Internal error: An expression services limit has been reached..." [119190] |
Summary: In the Summary tab of the Manager Dashboard’s Executive Overview tab, the historical performance analysis on the KPI card “Net Operating Income” fails with an error when Totals is selected in the Data Display Options. Resolution: Corrected by disabling the display of historical performance analysis data in the affected KPI cards. The Historical Performance Analysis table will not display for these cards, nor will the related icon ( |
| RF Dashboard - Sub-header logic with Previous Forecast Period when first period crosses years. Revisit headers in dialog [122072] |
Summary: In the Manager Dashboard, when the current period and prior period fall in different calendar years, the wrong year displays in the dashboard sub header. The Previous Forecast Period in the report sub header is derived using logic different from the other date displays. Resolution: Corrected by updating the logic for the Previous Forecast Period so that it displays the correct date. |
| RF Dashboard: Executive Overview tab, Historical Analysis with Total setting is producing inconsistent results when compared to the kpi card [124942] |
Summary: In the Summary tab of the Manager Dashboard’s Executive Overview tab, when Data Display options are set to Totals, initiatives data is not populating or being included in the Historical Performance Analysis drill tables, so the historical analysis data does not match what is displayed on the KPI card. Resolution: Corrected by adjusting the Axiom Query filters to allow for initiatives data to display. |
| [T3] Case Number 00448933 - RF 2.0 Month End Variance: Wrong Period Ending date [120970] |
Summary: In the Month End Variance report, the wrong Period Ending date is displayed at the top of the report even though the correct period is set in the Variance Comments Collection (VCC) Setup Utility. Resolution: Corrected by adding a date and period table to Axiom Query 2 for the report labels to reference. |
| Month End Variance labels are incorrect and do not match selections in Variance Comments Setup Utility [121492] |
Summary: In the VCC Setup Utility, the set Actual and Forecast periods do not match the periods displayed in the Month End Variance report, and the report column labels do not match the ones set in the VCC Setup Utility. Resolution: Corrected by adding logic that determines the Forecast RFPeriod date and then referenced this in the report column headers. |
| (2022.1) Rolling Forecasting R2 - VCC-related RFCODEs not delivered in new installs [131199] |
Summary: For the Month End Variance report, the VCC-related RFCodes are not being delivered with the default data in new installations. When a client configures the report using the Variance Comments Collection Setup Utility, saves, then opens the Month End Variance report, selects refresh variables and then saves, they receive an error. Resolution: Corrected by adding the missing VCC-related RFCodes. |
| Consolidated Summary: Formula Errors in Avg Daily Census, Free Cash Flow, Capital Spend % of EBIDA [134764] |
Summary: In the Consolidated Summary report, formula errors are causing issues with the indicators for Average Daily Census, Free Cash Flow (excluding Working Capital), and Capital Spend - % of Operating EBIDA. Resolution: Corrected by updating the formulas to reference the correct source amounts in their calculations. |
| RF Multi Scenario Comparison report - Scenarios 3-5 incorrect references resulting in incorrect calculations for multiple sections [135298] |
Summary: In the Multi-Scenario Comparison report, cell references for Debt Service Coverage, Days Cash on Hand, and Unrestricted Cash are incorrect, resulting in incorrect calculations. Resolution: Corrected by updating the formulas to reference the correct source amounts in calculations. |
| RF Multi Scenario Comparison report - Scenarios 2-5 incorrect references resulting in incorrect calculations for FTEs [135393] |
Summary: In the Multi-Scenario Comparison report, cell references for Total FTEs are incorrect, resulting in incorrect calculations for FTE metric. Resolution: Corrected by updating the formulas to reference the correct source amounts in calculations. |
| RF Multi Scenario Comparison report - Headers require logic or revisions for ForecastType [135837] |
Summary: In the Multi-Scenario Comparison report, the Header references require updates to cell references related to recognition of the Forecast Type. Resolution: Corrected by updating the Header formulas to recognize the Forecast Type for Actual versus Projected. |
| RF Multi Scenario Comparison report - Inpatient Discharges section queries K_Admissions - requires dynamic logic based on Drivers or separate section to pull both RFCodes [135838] |
Summary: In the Multi-Scenario Comparison report, the Inpatient Discharge section require updates to cell references related to Drivers to determine if Admissions or Discharge statistic is being used/referenced in metrics. Resolution: Corrected by updating the cell references related to Admissions and Discharges. |
| RF Multi Scenario Comparison report - Revisit quarters - Data differences based on ForecastType - Monthly calculating quarters and Quarterly hybrid with Q and Qtr field defs [135840] |
Summary: In the Multi-Scenario Comparison report, the Monthly and Quarterly values are not matching/calculating correctly due to incorrect logic associated with ForecastType for Actual versus Projected. Resolution: Corrected by updating the formulas dependent upon ForecastType to recognize the correct values for Actual versus Projected in the Quarterly columns. |
| RF Dashboard - Refresh variable selection of clear all requires reload of form [135870] |
Summary: In the RF Dashboard Filters panel, when the user clicks the Clear All button, an error appears that states, “Must specify a qualified column name that exists in the system.” It then requires the form to be re-loaded. Resolution: Corrected by making Scenario a required refresh variable. The data cannot populate without a Scenario selection, so a default is supplied in case the user does not select one. |
).The following table lists the resolutions for issues addressed in 2022.1.1, released June 20, 2022:
| Issue | Description |
|---|---|
| (2022.1.1) RF Patient Revenue Net Per Unit CM - Inconsistent calculation when making adjustments in forecast periods [143771] |
Summary: In the plan file Forecast worksheet, when users make an adjustment in a forecast period using the Patient Revenue Net Per Unit calculation method, the inflationary percentage adjustment was not included. Additionally, any One Time Adjustments (OTA) that came from the Volume calculation methods were not calculated correctly. Resolution: Updated the Patient Revenue Net Per Unit calculation method to include the % inflation changes. Also, for all monthly forecast period columns, updated the Average Rate Per Unit row to incorporate the inflation factor. Updated the Net Patient Revenue Including OTA formula to reference the correct cells. |
No client-facing issues were addressed in 2022.1.3, released on August 15, 2022.
IMPORTANT: Refer to the Axiom for Healthcare Suite Release Notes for additional known issues that have a suite-wide impact.
